Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Reporting] Clarify deprecation changes of the roles settings #121349

Merged

Conversation

tsullivan
Copy link
Member

@tsullivan tsullivan commented Dec 15, 2021

Summary

Closes #120263

Follows: #115125, #100427, #94966

Checklist

Delete any items that are not applicable to this PR.

Screenshots

Warning in the startup logs

image

Warning in the upgrade assistant

image

Warning seen if a role mapping to reporting_user exists

image

Warning seen if an existing user has the reporting_user role

image

@tsullivan tsullivan requested review from a team as code owners December 15, 2021 20:19
@tsullivan tsullivan added v7.17.0 v8.0.0 v8.1.0 release_note:skip Skip the PR/issue when compiling release notes deprecation_warnings (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Team:AppServicesUx labels Dec 15, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServicesUx)

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

` The "{fromPath}.roles.enabled" setting will default to false` +
` in a future release.`,
values: { fromPath },
`The default mechanism for Reporting privilege will work differently in future versions,` +
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

either "the Reporting privilege" or "Reporting privileges"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. I'll go with Reporting privileges

defaultMessage:
'Existing users have their Reporting privilege granted by a deprecated setting.',
`The default mechanism for Reporting privilege will work differently in future versions, and` +
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as above. Singular or plural for Reporting privilege.

defaultMessage:
'Existing users have their Reporting privilege granted by a deprecated setting.',
`The default mechanism for Reporting privilege will work differently in future versions, and` +
` this cluster contains users who have a deprecated role for this privilege.` +
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"has" instead of "contains"? contains makes me think that users are inside of the clusters.

}),
]
: []),

i18n.translate('xpack.reporting.deprecations.reportingRoleUsers.manualStepThree', {
defaultMessage: 'Create a custom role with Kibana privileges to grant access to Reporting.',
defaultMessage:
`Create one or more roles that grant the Kibana application` +
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would this work?

Go to Management > Security > Roles to create or more roles that grant the Kibana application privilege for Reporting.

Elsewhere, you use Reporting (capital R). Is that correct here?

defaultMessage: 'Existing roles are mapped to a deprecated role for Reporting privileges',
message: i18n.translate('xpack.reporting.deprecations.reportingRoleMappings.description', {
defaultMessage:
`The default mechanism for Reporting privilege will work differently in future versions, and` +
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as above. Singular or plural?

@@ -156,11 +166,17 @@ async function getRoleMappingsDeprecations(
: []),

i18n.translate('xpack.reporting.deprecations.reportingRoleMappings.manualStepThree', {
defaultMessage: 'Create a custom role with Kibana privileges to grant access to Reporting.',
defaultMessage:
`Create one or more roles that grant the Kibana application` +
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as above.

` Users assigned a reporting role specified in "xpack.reporting.roles.allow"` +
` will no longer have reporting privileges, they must be assigned an application privilege based role.`,
i18n.translate('xpack.reporting.deprecations.reportingRoles.manualStepFour', {
defaultMessage: `Grant reporting privileges to users by assigning one of the new roles.`,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it clear to users what the new roles are?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the new roles must be created by the admin

`Grant reporting privileges to users by assigning one of the new roles.` +
` Users assigned a reporting role specified in "xpack.reporting.roles.allow"` +
` will no longer have reporting privileges, they must be assigned an application privilege based role.`,
`Go to **Management > Security > Roles** to create one or more roles that grant` +
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed that bold formatting doesn't show up in the screenshots. Best to remove the **.

}),
]
: []),

i18n.translate('xpack.reporting.deprecations.reportingRoleUsers.manualStepThree', {
defaultMessage: 'Create a custom role with Kibana privileges to grant access to Reporting.',
defaultMessage:
`Go to **Management > Security > Roles** to create one or more roles that grant` +
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove bold formatting.

}),
]
: []),

i18n.translate('xpack.reporting.deprecations.reportingRoleMappings.manualStepThree', {
defaultMessage: 'Create a custom role with Kibana privileges to grant access to Reporting.',
defaultMessage:
`Go to **Management > Security > Roles** to create one or more roles that grant` +
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove bold formatting.

@tsullivan
Copy link
Member Author

@elasticmachine merge upstream

@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@tsullivan tsullivan merged commit f809278 into elastic:main Dec 16, 2021
@tsullivan tsullivan deleted the reporting/reporting-deprecation-wording-iii branch December 16, 2021 18:57
tsullivan added a commit to tsullivan/kibana that referenced this pull request Dec 16, 2021
…c#121349)

* [Reporting] Clarify deprecation changes of the roles settings

* updates per feedback

* update test snapshots

* minor fix

* fix i18n

* remove formatting marks

Co-authored-by: Kibana Machine <[email protected]>
tsullivan added a commit to tsullivan/kibana that referenced this pull request Dec 16, 2021
…c#121349)

* [Reporting] Clarify deprecation changes of the roles settings

* updates per feedback

* update test snapshots

* minor fix

* fix i18n

* remove formatting marks

Co-authored-by: Kibana Machine <[email protected]>
# Conflicts:
#	x-pack/plugins/translations/translations/ja-JP.json
#	x-pack/plugins/translations/translations/zh-CN.json
tsullivan added a commit that referenced this pull request Dec 16, 2021
… (#121444)

* [Reporting] Clarify deprecation changes of the roles settings

* updates per feedback

* update test snapshots

* minor fix

* fix i18n

* remove formatting marks

Co-authored-by: Kibana Machine <[email protected]>

Co-authored-by: Kibana Machine <[email protected]>
tsullivan added a commit that referenced this pull request Dec 16, 2021
… (#121447)

* [Reporting] Clarify deprecation changes of the roles settings

* updates per feedback

* update test snapshots

* minor fix

* fix i18n

* remove formatting marks

Co-authored-by: Kibana Machine <[email protected]>
# Conflicts:
#	x-pack/plugins/translations/translations/ja-JP.json
#	x-pack/plugins/translations/translations/zh-CN.json
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
(Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead deprecation_warnings release_note:skip Skip the PR/issue when compiling release notes v7.17.0 v8.0.0 v8.1.0
Projects
None yet
6 participants